Comments
-
My mistake! I made an error in the nat rules I now tested it internally and the config I did is correct but I made a mistake in a nat rule thanks
-
I know but I had to revert the ajustments i made as the wan 1 http connection dropped when I added/altered the config for wan 2. wan 2 http started working but that was not the plan on Monday I'll do some testing with a demo unit I have to see what happens then. I'll keep you posted
-
nope, the vpn connection works but I need to be able to connect to the client, so it has to get the same ip address on the vpn every time now it gets a random ip from the l2tp connection even when i set the client to use a fixed ip
-
when I connect to our own office that uses 172.27.0.0/20 with an external DHCP server (running on a macOS) and run the netstat -nr I get 172.27 ppp0 USc ppp0 172.28.0.254 172.27.3.248 UH ppp0 and then I can connect to all ip's in the /20 range it looks like the internal DHCP server return the wrong subnet-mask as the…
-
Hey KaranM, following the setting did not change anything to the vpn connection but the line at the bottom does help netstat -nr shows 192.0.0 ppp0 USc ppp0 192.0.0.1 192.0.0.223 UH ppp0 adding sudo route add -net 192.0.0.0/23 -interface ppp0 solves the problem and netstat -nr shows 192.0.0 ppp0 USc ppp0 192.0.0/23 ppp0…
-
Below the capture of a ping that works (strange thing is i can't see a ping captured to the not working ip: 192.0.1.21) *Packet number: 50* Header Values: Bytes captured: 66, Actual Bytes on the wire: 66 Packet Info(Time:04/21/2020 02:16:24.032): in:--, out:X0*, Forwarded, 2:2) VPN policy: WAN GroupVPN Ethernet Header…
-
because that would be the case if the customer work internally aswell
-
okay, i'll see if i can set this up today or tommorow (i restricted to work only 2 day a week for now)
-
you are correct but that is not the case here